Resolved issues:

none

Description of changes:

We're working to run integration tests on arm, but OpenSSL 1.0.2's build refuses to accept the -d debug flag.
Working around this by removing this flag for aarch64-linux only.

Call-outs:

The error:

nix develop .#openssl102                                                                                                 [18:06:19 2023-06-14]
error: builder for '/nix/store/99w05zkgabr14hywnfkj19mcmmr9pq3k-openssl-1.0.2.drv' failed with exit code 1;
       last 8 log lines:
       > unpacking sources
       > unpacking source archive /nix/store/c5dbamsp61aghc7vgw7rccw818z2l0qy-source
       > source root is source
       > patching sources
       > updateAutotoolsGnuConfigScriptsPhase
       > configuring
       > Operating system: aarch64-whatever-linux2
       > This system (debug-linux-aarch64) is not supported. See file INSTALL for details.
       For full logs, run 'nix log /nix/store/99w05zkgabr14hywnfkj19mcmmr9pq3k-openssl-1.0.2.drv'.

This appears to be a bug in the configure script of openssl102, where the $GUESSOS is expecting aarch64-whatever-linux2 vs debug-linux-aarch64 on line 674

The openssl wiki says -d isn't the only way to get a debug build, and we are using -g3:

...it's possible to quickly configure a "debug" build with ./config -d. However, you can often get into a more amicable state without the Electric Fence dependency by issuing:
./config no-asm -g3 -O0 -fno-omit-frame-pointer -fno-inline-functions"

https://wiki.openssl.org/index.php/Compilation_and_Installation#Debug_Configuration

Testing:

How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer?

Is this a refactor change? If so, how have you proved that the intended behavior hasn't changed?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.